Skill content updates: next-step link + Microsoft Foundry rename#5
Conversation
…I Foundry to Microsoft Foundry - Surface session next-step link (repo or next-steps site) in the 'What should I do after session' flow - Update two example CLI commands to use current product name 'Microsoft Foundry' Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
@copilot resolve the merge conflicts in this pull request |
pdebruin
left a comment
pdebruin
left a comment
There was a problem hiding this comment.
LGTM. Merge conflict resolved — auto-merges cleanly against current main. Both changes are correct: Foundry rename and nextStep link addition.
pdebruin
left a comment
pdebruin
left a comment
There was a problem hiding this comment.
Re-approving after merge conflict resolution. Changes are the same: Foundry rename + nextStep link.
|
@TianqiZhang — requesting your approval to unblock this merge. Branch protections require approval from someone other than the last pusher (me, after resolving merge conflicts). The PR itself is small and already reviewed:
No functional risk. Just needs your sign-off so we can merge. |
pdebruin
left a comment
pdebruin
left a comment
There was a problem hiding this comment.
Re-approving after Mike's trigger commits. All checks green.
3 participants
Updates SKILL.md with two targeted fixes:
1. Next-step link in Start Building flow
Adds reference to the session's next-step link (per-session repo or Build next-steps site) as the primary resource in the 'What should I do after session' workflow.
2. Product name update
Renames \Azure AI Foundry\ to \Microsoft Foundry\ in example CLI commands (lines 101, 110) to match current product naming.
This PR will grow to incorporate fixes for #3 (fabricated session data in examples) once we align on approach.